Fix/aws data api timezone validation #4918
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix AWS Data API timezone handling in Drizzle ORM
Problem
AWS Data API returns timestamps without timezone indicators (e.g.,
"2024-01-15 10:30:00.123"
), causing Drizzle to incorrectly interpret UTC timestamps as local time. This results in wrong relative times like "in 3 hours" instead of "3 hours ago".Solution
Enhanced
mapFromDriverValue
inPgTimestamp
to detect timezone indicators using regex/[+-]\d{2}:?\d{2}$|Z$/
. Whentimestamptz
columns lack timezone info, automatically append 'Z' to force UTC interpretation.Before:
After:
Impact
Type of Change
Just copy and paste this directly into the GitHub PR description field! 🎯